Fix #59: Added timeout tracker to check session expiration #134
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue Number
fixes #59
Describe the changes you've made
I have added a timeout tracker which periodically checks if the session has expired or not. The session limit is set to
1 hour
by default. In order to change the limit, we can add asessionLimit
field in thesrc/config.json
, and provide the number of seconds as its value.For example, if we want the session to be of
20 seconds
, as shown in the demo below, the file should beThe basic flow is -
expirationTime
is saved into in local storageDescribe if there is any unusual behavior (Any Warning) of your code(Write
NA
if there isn't)NA
Additional context (OPTIONAL)
NA
Test plan (OPTIONAL)
NA
Checklist
Provide a Deployed link of route/page that needs to review
screen-capture.3.mp4